GPU use for preview generation

bob frost · ‎Sep 05, 2025

My GPU is an RTX 470 with 12 GB of RAM. Adobe says that to use the new preview generation in LR Classic 14.5.1 it needs 16GB of RAM. So I tried it with my GPU. On AUTO (in Performance) it uses a little of the GPU, but I have to switch it to ON to force LR to use more of the GPU. Even then, it only uses a maximum of 30% of the 12GB available. Not sure whether it is any faster, but it does lower CPU use significantly and thus CPU temperature. So why does Adobe say it needs 16GB, when it doesn't even use more than about 4GB of my current GPU? Bob Frost

bob frost · ‎Sep 04, 2025

I was intrigued by LR Classic 14.5 and its use of the GPU for preview generation, so I updated the CCD to the latest version (6.7.0.278 which resulted in loads of Heartbeat files produced by the Adobe Crash Processor as usual). I solved that this time by searching for all instances of the Adobe Crash Processor - 4 - and renaming them so they cannot run. Then I could update PS, LR, BR, and ACR without all the crash stuff. I'll discuss the preview generation on the LR Classic forum. It would be nice if we had an update to CCD that solved the problem with the Adobe Crash Processor. Bob Frost

bob frost · ‎Aug 11, 2025

I replied to this post days ago, by the email option, but it doesn't seem to get to this list. So I have retrieved it from my email sent folder and copied it here:- Thank you, thank you! That has saved me hours of work. I did what you both suggested, and exported all the keywords to a .csv file, opened that in Excel, filtered it on 'N' (not exported) and printed out the list of offending keywords. Of my 1700 or so keywords just over 100 were not exportable, so I then did as John suggested and corrected them manually. What I don't understand is why those 100 or so keywords had not got the export checkboxes checked. So thank you both again. Bob Frost

bob frost · ‎Aug 08, 2025

Task Manager and Resource Monitor. I've now solved the problem completely by restoring my Win 11 system to the April '25 version of the CC set of programs (6.6.0.611), and the corresponding versions of LR Classic (14.3.1) and PS (26.7). Adobe Crash Processor does not appear now, and every thing seems to run smoothly as it did before the CC update. If and when Adobe solves the problem with the latest CC updates, I will update. I've lost the new AI stuff in LR, but as the old saying goes "What you've never had, you won't miss!" Bob Frost

bob frost · ‎Aug 05, 2025

Hi Srishti, I'm not bothering you with the complete details you asked for as I noted that the fault lay with a video module, so I checked my graphics card driver which I thought was up-to-date (June 25), but it seems there has been a July update. So I have clean-installed the July Studio update and will wait a few days to see if that has solved the problem. Bob Frost

bob frost · ‎Aug 05, 2025

Immediately after rebooting, the adobe crash processor leaps into action. None of my main apps are running, nor is the desktop app (set not to run at login or after closing). So itmust be one of the other many files in the Creative Cloud Mess. There are three or four exe's that run and dozens of other files in the Creative Cloud folders, all of which were updated along with the desktop app when this problem started. I can kill the crash processor and stop anymore '*heartbeat.db-journal' files being produced and the existing ones slowly disappear. It didn't happen before the last update of the Mess. bob Frost

bob frost · ‎Aug 04, 2025

Description Faulting Application Path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe Problem signature Problem Event Name: BEX64 Application Name: Lightroom.exe Application Version: 14.4.0.8 Application Timestamp: 68415920 Fault Module Name: video_toolkit.dll_unloaded Fault Module Version: 14.4.0.0 Fault Module Timestamp: 6841579b Exception Offset: 00000000002ecddd Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.26100.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 76a1 Additional Information 2: 76a173c26a6dc2e3cd83ac8fd9f8bdb9 Additional Information 3: 7b3f Additional Information 4: 7b3f634c955ac91fe3f1e745337a968a Extra information about the problem Bucket ID: 95cfb192acb60cc6c2df5e8c4654c091 (1359909569057570961) Is there anything I can do about this? Bob Frost

bob frost · ‎Aug 03, 2025

Just looked at a few keywords and some have the export options ticked and some don't. Why? Bob Frost

bob frost · ‎Aug 03, 2025

I've never done that for any keywords. But I have just found that at the top of the keywords panel, the line that says 'Enter keywords has three options, one of which says 'Will export' and the only keyword that shows then is the one that is exported. So are you saying that I have to go to each keyword, and select it to be exported? I have thousands of keywords. Why are some exported and some not? I've never selected ever! Bob Frost

bob frost · ‎Aug 03, 2025

I have just exported 120,000 nefs to jpgs and most of the keywords in the nefs are missing from the jpgs. It is set to export all metadata including personal and location. It doesn't seem to matter whether the keyword hierarchy box is ticked or not. Example, a nef with the keywords 'lanzarote', 'playa blanca', and 'Liz' are exported, but the jpg only contains one keyword 'playa blanca'. The file info has been verified with Photoshop file info. What is happening? Bob Frost

bob frost · ‎Jul 21, 2025

Hi Kglad, Simply turning off the actual creative cloud exe file does not stop the crashes, so the fault must lie in the other processes that are installed/updated along with the main app. Bob Frost

bob frost · ‎Jul 18, 2025

Hi Ian, Providing I run CC Desktop 6.6.0.611 (issued in April this year) along with LR Classic 14.3.1 and Photoshop 26.7, everything runs smoothly with not problems showing up in Win11 Resource Monitor. BUT as soon as I try to update LR or PS, CC Desktop insists on updating itself to 6.7.0.278 and then Adobe Crash Processor starts producing up to 30 instances of CRDaemonHeartbeat.db-journal files. I assume this means that one of the dozen or so background progs that are updated with CC Desktop app is crashing. I have not noticed any effect on LR Classic or PS so far, but I don't like progs misbehaving on my computer! I have regular system backups and have gone back several times to prove that is it simply this update of CC desktop group of files that is causing the problem. Any solution in sight from Adobe? I understand that the Adobe Crash processor report to Adobe. I have posted this on the CC Desktop forum to see whether that gets a reply. Bob Frost

bob frost · ‎Jul 18, 2025

Providing I run CC Desktop 6.6.0.611 (issued in April this year) along with LR Classic 14.3.1 and Photoshop 26.7, everything runs smoothly with not problems showing up in Win11 Resource Monitor. BUT as soon as I try to update LR or PS, CC Desktop insists on updating itself to 6.7.0.278 and then Adobe Crash Processor starts producing up to 30 instances of CRDaemonHeartbeat.db-journal files. I assume this means that one of the dozen or so background progs that are updated with CC Desktop app is crashing. I have not noticed any effect on LR Classic or PS so far, but I don't like progs misbehaving on my computer! I have regular system backups and have gone back several times to prove that is it simply this update of CC desktop group of files that is causing the problem. Any solution in sight from Adobe? I understand that the Adobe Crash processor report to Adobe. Bob Frost

bob frost · ‎Jul 16, 2025

Thanks for your replies Ian. The reason why I posted here is that the problem with CC desktop seemed to be affecting LR Classic, and I hoped someone here would have an answer. I hadn't heard of the CC Desktop forum before; it hasn't been listsed on any lists of forums I've seen. But now that you have pinpointed it, I will go there on a rainy day, and see what they have to say. I thought that by editing the desktop prefs, I had turned it off, but it has reappeared today! A persistant little ********. Bob Frost

bob frost · ‎Jul 15, 2025

Well, the Adobe website has this: "Download and install apps, share files, find fonts and Adobe Stock assets, set preferences, and more — all from the Creative Cloud desktop app. It installs automatically when you install your first Creative Cloud app." So they refer to it as the 'Creative Cloud desktop app'. It is installed and is necessary for the installation of LR, PS, and all the Creative Cloud apps. It turns itself on and runs in the background whenever I use LR, PS, etc. However, I have found that if I go to CC desktop Prefs, I can turn it off and prevent it running in the background. That stops the Adobe Crash Handler appearing in Windows Resource Monitor, while I can still use LR Classic. Just have to turn it back on when I want updates to LR, PS, etc. Since the function of Adobe Crash Handler is to report crashes to Adobe, we might get a fix for this one day. Bob Frost

bob frost · ‎Jul 14, 2025

Creative Cloud Desktop. It starts itself at logon.

bob frost · ‎Jul 13, 2025

I've started a new thread since my last post about printer profiles mentioned a second problem in LR Classic where the Help/LR Classic option does not appear. That was cured by reinstalling LR, but it has now reappeared. After reading up on this, I followed one recommendation to go to ControlPanel/programs/uninstall-repair for the CC Desktop. I did the repair for the CC desktop and that cured the problem - the Help in LR Classic now worked again. Watching the Resource Monitor showed a lot of activity of the Adobe Crash Processor. So something is going wrong somewhere with the CC Desktop it seems? bob Frost

bob frost · ‎Jul 08, 2025

Accidentally I have solved this problem. Yesterday I wanted to read up on the Enhance options in LR Classic, so I clicked on Help/LR Classic Help but got no response. Tried again, still no response. Closed LR, rebooted, opened LR and tried again but still no response. Mmmm! I couldn't think of anything that could be stopping Help from working, so eventually I decided to get tough with LR! I used CC Desktop to uninstall LR, clicking on the option to retain Prefs etc. I then rebooted Windows, and used CC Desktop to reinstall LR Classic. All seemed to go smoothly and when I opened LR and clicked on Help it worked!! Problem solved. After reading up on the recent Enhance options, I edited and image and went to print it. At that point I suddenly wondered if the reinstallation of LR had affected my previous problem (described above) with printer profiles. I clicked on the printer profile offered in the Print Job/Color management dialog but the same 'random' selection of printer profiles was offered as before. I didn't click on 'Other' profiles because recent experience had shown this caused LR to lock up completely. However, further thought led to me trying that, and Lo and Behold, up popped the desired dialog with a list of all my printer profiles in Sys32/spool/drivers/color that I could select to appear in LR. So two problems solved by reinstallation of LR Classic. I don't think I've ever had to uninstall and reinstall LR in all the years I've been using it (since version 1). OK, I've had to trash Prefs occasionally, and copy a catalog to a new one to get rid of accumulated rubbish, but never had to reinstall LR. I will now remember this as a new problem-solving option. I'm surprised no-one suggested this! bob Frost

bob frost · ‎Jun 30, 2025

I've been making printer profiles for years using iMatch, and have had no problems with LR Classic until now. At the moment when I create a template and go to choose a profile to put in it, I either get 'managed by printer' or one or two old profiles even of different printers. After many hours of playing about (including trashing Prefs) the only way I can get the correct profile (from the sys32/spool/drivers/color windows folder) to register in LR is to edit the printer template (in the LR Settings folder) manually and delete the autoincluded profile and substitute the new one, saving the altered template. That seems to work and LR shows the new profile after closing and reopening. The one thing I must NOT do is to click on OTHER in the LR profiles list - that just locks LR solid, and the only way out is to use Task Manager to exit LR, reboot and start again!! I'm not the only one to find this - I read another post where clicking on Other did the same thing. So what is the problem with the latest LR Classic? It never used to behave like this. Bob Frost TOPICS Windows

bob frost · ‎Jun 26, 2025

I've been making printer profiles for years using iMatch, and have had no problems with LR Classic until now. At the moment when I create a template and go to choose a profile to put in it, I either get 'managed by printer' or one or two old profiles even of different printers. After many hours of playing about (including trashing Prefs) the only way I can get the correct profile (from the sys32/spool/drivers/color windows folder) to register in LR is to edit the printer template (in the LR Settings folder) manually and delete the autoincluded profile and substitute the new one, saving the altered template. That seems to work and LR shows the new profile after closing and reopening. The one thing I must NOT do is to click on OTHER in the LR profiles list - that just locks LR solid, and the only way out is to use Task Manager to exit LR, reboot and start again!! I'm not the only one to find this - I read another post where clicking on Other did the same thing. So what is the problem with the latest LR Classic? It never used to behave like this. Bob Frost

bob frost · ‎Mar 17, 2025

Why does my Creative Desktop keep telling me that my Photoshop needs updating when it has already updated it to the version it wants to install? The only way out of this is to tell it to install it again, and it then starts doing so, and soon realises its mistake and stops and tells me it is updated! Grrrr! It does this even when it has updated itself first|! Bob Frost

bob frost · ‎Feb 18, 2025

I've noticed that every time there is a major update to LR Classic it writes the number of the new update to every image file and xmp. I only noticed this when I go to backup my image files and find that they all need backing up! Of course I could turn off copying to xmp and jpgs etc. I can't see any need for this - recording the new update when an image is edited is fine, but no reason to do it to all of them when not even being looked at. Bob Frost

bob frost · ‎Nov 02, 2024

Is it possible to print contact sheets of the face previews in People screens? Bob Frost

bob frost · ‎Sep 11, 2024

OK, I've just done it again. Created a new catalog, imported the same 50 nefs, and lo and behold it has created 2560, 1280 and 640 previews! That is what you would expect with a 2560 monitor. But when I then created 1:1 previews, it made 8256 and 4128 previews, as expected for 8256 images(?), but altered the existing previews to 2064, 1032, and 320. The previous 2560, 1280 and 640 previews have disappeared! So in this second test, the initial creation of standard previews was in relation to the monitor size, but the second creation (using Build 1:1 previews) changed them all to be in relation to the image size(except for the 320 size). Make of that what you will! Perhaps all this was best hidden in .lrprev files. Bob Frost

bob frost · ‎Sep 11, 2024

Hi Ian, I've read your reply three times, but it does not tally with what LRC 13.5 has actually done in my test. To reiterate, the NEF files imported into my test catalog were fullsize from my Nikon Z8 camera so had dimensions of 8256x5504. They were not cropped either in camera or in LRC (the xmps that they had in my main catalog were left behind). On importing LRC automatically created three new preview files for each image - 2064, 1032, and 320 (according to their filenames). These seem to be correct sizes of 1/4, 1/8, and 1/32 of the actual file size (8256). Why there was no 1/16 is presumably known only by the LRC team. When the 1:1 previews were made these were 4128 and 8256, the 1/2 and fullsize previews. On deletion of 1:1s, only the fullsize 8256 was deleted leaving the 1/2 size (4128) behind. What seems to be misleading is the default catalog prefs entry of 'Auto (2560)'. Wondering about that for a while, I suddenly realised that it was the monitor size (Eizo CG 2730) - 2560x1440. The actual previews are not directly related to the monitor size but to the file size (8256). I hope this clears things up? Bob Frost

bob frost · ‎Sep 10, 2024

Not quite finished! To investigate the 1:1 previews in the new preview sytem of LRC 13.5 I created a new catalog and imported 50 nefs (about 45Mp each). LRC created new previews according to its defaults (auto - 2560 and medium quality), and looking at the new previews I have three for each image - 320, 1032, and 2064 in size.I then created 1:1 previews which added 4128 and 8256 in size. Then deleting the 1:1 previews only deleted the largest size that it had created - 8256 - and left the 4128 size that was created by the build 1:1 preview command. Interesting. No .lrprev files at all, but three .lrfprev files for the three faces in those images. So to sum up, using 'build 1:1 previews' creates two larger sizes of the new format previews, but deleting them only deletes the largest. Happy Lightrooming! Bob Frost

bob frost · ‎Sep 08, 2024

Hi Johan, I don't use publishing services and wouldn't even dream of syncing my images to the cloud! I know, I'm a dinosaur! I don't know whether the copying of previews during and export of the catalog to a new catalog does clean up the previews. I was just reporting what someone else said in another thread. I used to manually cleanup the catalog using SQlite DB browser until I heard that exporting the catalog did the trick. I have had to do this a few times over the years, usually after an upgrade to a new version catalog. I have not had to do this lately, so LRC must have improved its upgrade process. As to cleaning up previews, I still do that manually. It was usually simple to spot previews that are incomplete or duplicated, and delete them. This current conversion of .lrprev files to separate-size files without an extension has left me with a lot of .lrprev files that I have deleted manually without an effect on LRC behaviour. I suppose I could use my last week's backup of LR to test whether exporting the catalog with previews does cleanup these leftover .lrprev files (assuming they are leftovers!). Do you know why the .lrfprev files have not been converted? Is it because they only contain one size of people preview already? Coming back to your point about publishing services and syncing, couldn't Adobe sort this out so that exporting a catalog didn't upset them? And couldn't Adobe give us a good repair tool for catalogs? They do repair some catalogs, so they must have one. Bob Frost

bob frost · ‎Sep 06, 2024

Deleting the current previews is simple, I agree. But regenerating them if you have a couple of hundred thousand files takes ages, even with the current ability to generate previews in parallel. If you include previews in an export to another catalog surely it just copies the existing previews rather than rebuild them as you suggest? Bob Frost

bob frost · ‎Sep 06, 2024

To finish this saga, I deleted all the 1348 leftover .lrprev files on the assumption that they were simply orphaned previews (they all had the same create date of a couple of years ago). I then opened LRC and left it for a couple of hours to update its preview.db file, and then ran 'Build Standard Previews', which said there were none to build. So I was probably right in my assumption, and LRC runs fine. I can't detect any difference in performance with the new preview files, but maybe a hundredth or thousandth of a second is important to programmers! Bob frost

bob frost · ‎Sep 06, 2024

In another thread I read that if you use 'Export to another catalog' with previews (but not images), it leaves behind any rubbish in the catalog, but also in the previews. I've done this in the past to get rid of rubbish in the catalog and improve performance, but I haven't done it with the previews. Worth a try. Bob frost

bob frost

bob frost

Activity

GPU use for preview generation

Re: CC Desktop update causing crashes?

Re: exported keywords to jpgs are missing

Re: CC Desktop update causing crashes?

Re: LR Classic stops working

Re: CC Desktop update causing crashes?

LR Classic stops working

Re: exported keywords to jpgs are missing

Re: exported keywords to jpgs are missing

exported keywords to jpgs are missing

Re: CC Desktop update causing crashes?

Re: CC Desktop crashing?

CC Desktop update causing crashes?

Re: CC Desktop crashing?

Re: CC Desktop crashing?

Re: CC Desktop crashing?

CC Desktop crashing?

Re: printer profiles missing

printer profiles missing

Lightroom Classic Not Recognizing New Printer Prof...

Photoshop updates

Re: LRc 14 reading every single files images in my...

Contact sheet from People screens?

Re: Preview files have multiplied

Re: Preview files have multiplied

Re: Preview files have multiplied

Re: Good way to clean up old previews?

Re: Good way to clean up old previews?

Re: Preview files have multiplied

Re: Good way to clean up old previews?